Skip to content

Conversation

@myankelev
Copy link
Member

@myankelev myankelev commented Jul 21, 2025

When the test is run now the reason for the failure will be requested providing further feedback.


Progress

  • Change must be properly reviewed (1 review required, with at least 1 Reviewer)
  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue

Issue

  • JDK-8360562: sun/security/tools/keytool/i18n.java add an ability to add comment for failures (Enhancement - P4)

Reviewers

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/26412/head:pull/26412
$ git checkout pull/26412

Update a local copy of the PR:
$ git checkout pull/26412
$ git pull https://git.openjdk.org/jdk.git pull/26412/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 26412

View PR using the GUI difftool:
$ git pr show -t 26412

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/26412.diff

Using Webrev

Link to Webrev Comment

@bridgekeeper
Copy link

bridgekeeper bot commented Jul 21, 2025

👋 Welcome back myankelevich! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

@openjdk
Copy link

openjdk bot commented Jul 21, 2025

@myankelev This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

8360562: sun/security/tools/keytool/i18n.java add an ability to add comment for failures

Reviewed-by: rhalade

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been 1265 new commits pushed to the master branch:

As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

@openjdk openjdk bot changed the title JDK-8360562: sun/security/tools/keytool/i18n.java add an ability to add comment for failures 8360562: sun/security/tools/keytool/i18n.java add an ability to add comment for failures Jul 21, 2025
@openjdk openjdk bot added the rfr Pull request is ready for review label Jul 21, 2025
@openjdk
Copy link

openjdk bot commented Jul 21, 2025

@myankelev The following label will be automatically applied to this pull request:

  • security

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command.

@openjdk
Copy link

openjdk bot commented Jul 21, 2025

@myankelev Please do not rebase or force-push to an active PR as it invalidates existing review comments. Note for future reference, the bots always squash all changes into a single commit automatically as part of the integration. See OpenJDK Developers’ Guide for more information.

@mlbridge
Copy link

mlbridge bot commented Jul 21, 2025

Webrevs

@bridgekeeper
Copy link

bridgekeeper bot commented Aug 18, 2025

@myankelev This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply issue a /touch or /keepalive command to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration!

@bridgekeeper
Copy link

bridgekeeper bot commented Sep 16, 2025

@myankelev This pull request has been inactive for more than 8 weeks and will now be automatically closed. If you would like to continue working on this pull request in the future, feel free to reopen it! This can be done using the /open pull request command.

@bridgekeeper bridgekeeper bot closed this Sep 16, 2025
@myankelev
Copy link
Member Author

/open

@openjdk openjdk bot reopened this Sep 16, 2025
@openjdk
Copy link

openjdk bot commented Sep 16, 2025

@myankelev This pull request is now open

@myankelev
Copy link
Member Author

/open

@openjdk
Copy link

openjdk bot commented Sep 16, 2025

@myankelev This pull request is already open

@rhalade
Copy link
Member

rhalade commented Oct 2, 2025

Is this enhancement requested related to some test failure that were not clear to triage? The fix looks good but is there a need for it?

@myankelev
Copy link
Member Author

myankelev commented Oct 2, 2025

Is this enhancement requested related to some test failure that were not clear to triage? The fix looks good but is there a need for it?

Yes, the error was missed several times before, as there was no comment. The error itself turned out to be a non-issue, but it was still missed and triaging it took quite a bit of time.

This particular issue was documented here JDK-8360400. After evaluation the decision was made to remove the test case after JDK-8360416.

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Oct 2, 2025
@myankelev
Copy link
Member Author

/integrate

@openjdk
Copy link

openjdk bot commented Oct 3, 2025

Going to push as commit ebb6fd7.
Since your change was applied there have been 1272 commits pushed to the master branch:

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot added the integrated Pull request has been integrated label Oct 3, 2025
@openjdk openjdk bot closed this Oct 3, 2025
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review labels Oct 3, 2025
@openjdk
Copy link

openjdk bot commented Oct 3, 2025

@myankelev Pushed as commit ebb6fd7.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

integrated Pull request has been integrated security [email protected]

Development

Successfully merging this pull request may close these issues.

3 participants